ICAO PBN Implementation Plan - APAC

 

ICAO Asia Pacific Office

 

APANPIRG/18 Meeting  (3-7 September 2007) considered that implementation of PBN in the region was very important and would yield efficiency and safety benefits . Noting that the participation of all stakeholders in the development of a PBN implementation plan was essential, the meeting agreed that the establishment of a PBN Task Force would likely be the best vehicle to achieve the objective of an accelerated PBN implementation programme regionally. 

 

                        Conclusion 18/52 –Establishment of a Regional Performance Based Navigation Task Force (PBN/TF)

That, an Asia/Pacific PBN Task Force, with terms of reference as outlined in Appendix A to the APANPIRG/18 Report on Agenda Item 3.5, be established to develop a PBN implementation plan for the Asia/Pacific Region and address related regional PBN implementation issues.

 

The First Meeting of the Performance Based Navigation Task Force was held in Bangkok, Thailand from 9 to 11 January 2008.

The Meeting was attended by 50 participants from Australia, Bhutan, China, Hong Kong China, India, Japan, Malaysia, Maldives, New Zealand, Pakistan, Philippines, Singapore, Sri Lanka, Thailand, United States, Vietnam, IATA and IFALPA and ICAO.

 

List of PBN Implementation Issues and Two Task Lists were developed. These included:

Establishing current levels of State operations and initial intent; Establishing  list of local and general issues which should be addressed during implementation of PBN; Providing Training Framework and individual training packages for pilots, controllers, regulators etc; Establishing On-The-Job Training specifically with regard to PBN Procedure Design and Establishing ability and intent of States to offer participation and Provision of Model Operational and Air Worthiness Approval Documentation.

Table of Contents for the Regional PBN Implementation Plan was developed and task allotted to respective TF members.

Subsequently the PBN Task Force met three times as follows:

Second Meeting at Bangkok:  1-3 April 2008;

Third Meeting at Bangkok:     14 – 17 July 2008; and

Fourth Meeting at Japan:         4 – 6 March 2009 (68 paticipants).

The PBN/TF/4 Meeting was preceded by the ICAO-JCAB Asia/Pacific PBN Implementation Seminar which was hosted by the Japan Civil Aviation Bureau (JCAB) at the Aeronautical Safety College, Osaka, Japan on 2 – 3 March 2009. Eighty four (84) participants representing Australia, Bangladesh, Cambodia, China, Hong Kong China, Fiji, Indonesia, Japan, Lao PDR, Malaysia, Maldives, New Zealand, Philippines, Republic of Korea, Singapore, Sri Lanka, Thailand, United States, Viet Nam, IATA, IFALPA and Jepessen attended the Seminar.  

At the PBN/TF/4 Meeting, twenty (20) of the APAC States provided an update on their status of implementation. Eighteen (18) Conclusions/Action Items were agreed to at the Meeting.  

At the PBN/TF/4 Meeting the Regional PBN Implementation Plan Subgroup Task List and the State PBN Implementation Plan Subgroup Task List from PBN/TF/1 Meeting continued to be reviewed and updated.

APANPIRG/19 Meeting (1-5 September 2008) approved the Asia /Pacific Regional PBN Implementation Plan as an Interim Edition (Version  - V 0) pending subsequent reviews by RASMAG, CNS/MET/SG and ATM/AIS/SAR/SG. Version V 0.2 of the Plan was finalized by PBN/TF/4 meeting.

 

APANPIRG/19 agreed to extend the term of the PBN/TF till its next meeting in September 2009 (two additional PBN TASK Force meetings being held)

 

All Meeting Reports and PBN Implementation Plan have been provided to APAC States.

 

APAC States have been requested to use the Interim edition of the APAC Regional PBN Implementation Plan as guidance for development of their respective State Plans.

 

 

Achievements

 

APAC Regional PBN Implementation Plan Interim Edition (V 0.2) developed.

 

Twenty three (23) States  and four (4) International Organizations have nominated their PBN Focal Points.

 

The PBN Task Force includes 27 Members  representing 10 States and 4 international Organizations.

 

PBN Seminar held in Japan in March 2009. CAD Hong Kong has offered to host the next PBN Seminar in February 2010.

 

Asia Pacific Flight Procedure Programme Office is being established in Beijing, China (expected to be operational in October 2009)

 

Model Operational and Airworthiness Approval Documentation provided to States.

 

Summary of PBN Implementation Plan

 

 

Short Term (2008-2012)*

Airspace

Preferred Nav. Specifications

Acceptable Nav. Specifications

Route – Oceanic

RNP 4

RNAV 10

Route – Remote continental

RNP 4

RNAV 10

Route – Continental en-route

RNAV 2, RNAV 5

TMA – Arrival

RNAV 1 in radar environment and with adequate navigation infrastructure.

 

Basic-RNP 1 in non-radar environment

 

TMA – Departure

RNAV 1 in radar environment and with adequate navigation infrastructure.

 

Basic-RNP 1 in non-radar environment

 

Approach

RNP APCH with Baro-VNAV in most possible airports

 

RNP AR APCH in airport where there are obvious operational benefits.

 

Implementation Targets

·         RNP APCH (with Baro-VNAV) in 30% of instrument runways by 2010 and 50% by 2012 and priority should be given to airports with operational benefits

·         RNAV 1 SID/STAR for 50% of international airports by 2010 and 75% by 2012 and priority should be given to airports with RNP Approach

·         Re-defining existing RNAV/RNP routes into PBN navigation specification by 2012

·         Implementation of additional RNAV/RNP routes

 

 

* Note: Early completion of an implementation is encouraged within the timeframe on the basis of coordination between affected States and airspace users.

 

 

 

Medium Term (2013-2016)*

Airspace

Preferred Nav. Specification

Acceptable Nav. Specification

Route – Oceanic

RNP 2**, RNP 4

RNAV 10

Route – Remote continental

RNP 2

RNAV 2, RNP 4, RNAV 10

Route – Continental en-route

RNAV 1, RNP 2

RNAV 2, RNAV 5

TMA – Arrival

Expand RNAV 1 or RNP 1 application

 

Mandate RNAV 1 or RNP 1 approval for aircraft operating in higher air traffic density TMAs

 

TMA – Departure

Expand  RNAV 1 or RNP 1 application

 

Mandate RNAV 1 or RNP 1 approval for aircraft operating in higher air traffic density TMAs

 

Approach

Expansion of RNP APCH (with Baro-VNAV) and APV

 

Expansion of RNP AR APCH where there are operational benefits

 

Introduction of landing capability using GNSS and its augmentations

 

Implementation Targets

·         RNP APCH with Baro-VNAV or APV in 100% of instrument runways by 2016

·         RNAV 1 or RNP 1 SID/STAR for 100% of international airports by 2016

·         RNAV 1 or RNP 1 SID/STAR for 70% of busy domestic airports where there are operational benefits

·         Implementation of additional RNAV/RNP routes

 

 

* Note 1: In circumstances where affected States are agreeable to completing an implementation in advance of the timeline, early implementation is encouraged on the basis of coordination between affected States and airspace users.

 

** Note 2: Related CNS requirements and operational procedures for RNP 2 application in Oceanic Airspace are yet to be determined.

 

 

Long Term Implementation Strategies (2016 and beyond)

 

In this phase, GNSS is expected to be a primary navigation infrastructure for PBN implementation. States should work co-operatively on a multinational basis to implement GNSS in order to facilitate seamless and inter-operable systems and undertake coordinated  research and development programmes on GNSS implementation and operation.

 

On going

 

In depth appraisal of the PBN TF Outputs against the PBN TF Terms of Reference completed at PBN/TF/4 meeting and  the following Conclusions and Actions agreed to:

 

Ø  The APAC PBN TF agrees to continue an annual review of the Asia-Pacific Regional PBN Implementation Plan

Ø  Develop an up-to-date archive of all relevant guidance materials for each PBN implementation step as outlined in the PBN manual

Ø  Arrange future annual PBN implementation seminars to serve as a forum for exchanging expertise and implementation experiences and invite interested States who would like to host future seminar to make a formal proposal at the next PBN TF meeting and to invite industry representatives to attend the seminar

Ø  The APAC PBN TF agrees to continue coordination with other regional PBN task forces and the Global PBN Task Force to ensure harmonization of PBN implementation

Ø  States to present their PBN Implementation Plan and to provide progress reports on the development of the State Plan at the next PBN TF meeting

Ø  Request the Task Force Chairperson and Rapporteurs to develop a common template for State PBN Implementation Progress Report to be reviewed by the next PBN TF meeting

Ø  The APAC PBN TF agreed to develop a regional PBN progress report to be reported annually to CNS/MET and APANPIRG and to be posted on ICAO APAC and ICAO Global PBN web site

Ø  The APAC PBN Task Force considers itself a suitable forum to facilitate and harmonize terminal and en-route PBN implementation in the Asia Pacific Region. Therefore, the Task Force requests APANPIRG to consider adding the following task into the Task Force’s TOR. “Facilitate and coordinate the harmonized implementation of PBN for terminal and en-route applications in the Asia Pacific Region

 

In view of the appraisal carried out of the PBN TF Outputs against the PBN TF Terms of Reference the Meeting developed a detailed Implementation Task List of work that still needed to be carried out to ensure effective and smooth implementation of PBN in the Asia Pacific Region.

 

Implementation Task List

 

·                     General

 

o        Fleet readiness statistics for different navigation specification

o        General guidance on aircraft types and their configurations that have capability for different PBN navigation specifications

o        Prepare performance measuring methodology to assess success of PBN  implementation

 

·                     En-route

 

o        Identify appropriate navigation specification for existing pre-PBN RNAV routes.

o        Identify and prioritize suitable city-pairs which can benefit from PBN implementation

o        Develop a status report on areas of en-route harmonization gaps.

o        Identify regional route structures for application of RNAV 10 and RNP 4 separation standards.

 

·                     Terminal Area & Approach

 

o        Create a status report of WGS-84 implementation within the APAC

o        Create a status report of compliance with the Annex 15 Electronic Terrain and Obstacle Data (ETOD) requirements

o        Identify proper strategies for PBN applications for helicopter in the Asia-Pacific

o        Identify and prioritize suitable airports and terminal areas which can benefit from PBN implementation

 

 

Recognizing that the PBN planning activities for the Asia-Pacific are nearing completion and acknowledging the Task Force’s willingness to support actual PBN implementation, the APAC PBN Task Force has requested working papers regarding revision of the Task Force’s work structure to be submitted for consideration at PBN TF/5.

 

The Fifth Meeting is scheduled for 15 – 17 July 2009.